Systems, methods, and manufactures for providing network services including mobile services to a location

ABSTRACT

Systems, methods, and computer readable media are directed to pooling resources in a mobile network. The method includes allocating baseband resources between a plurality of virtual baseband engines supporting the mobile network. The method includes determining a change in a usage of the mobile network. Additionally, the method includes re-allocating, in response to the change in the usage of the mobile network, the baseband resources between the plurality of virtual baseband engines. Systems, methods, and computer readable media are also directed to providing services at a location that includes a mobile network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to 62/140,027 filed Mar. 30, 2015, thedisclosure of which is incorporated by reference herein in its entirety.

BACKGROUND

Demands for end-user cellular mobile performance, also known as MobileBroadband (“MBB”), are expected to increase by factors of 1000 over thenext 5 years with MBB connections expected to reach nearly 6 billion by2020. The forecast for these demands are concentrated on areas wherethere are high-densities of people, especially of an affluent enoughnature that they are utilizing the latest in mobile devices (smartphonesand similar user equipment). In addition to humans, an influx ofembedded wireless radios within a wide array of machines and personaldevices (cars, appliances, etc.) will further increase demands, thisoutgrowth is known as Internet of Things (IoT) or Machine to Machine(M2M) and is anticipated to 15 billion connected devices on the globalnetworks by 2020. Bandwidth-consuming applications, including videocommunications and streaming of broadcast quality video, may push thedemand for bits-per-second on a per user basis. As a result, theutilization of available, shared spectrum is critical—requiring a higherquantity of smaller-sized cells that can support larger quantities ofusers while delivering increases in each user's performance.

Small cell technology set out to address this growth. However, thenature of most small cells is such that they tend to have limitations insignal delivery, require many to cover an area, are limited in theirability to support an influx of active users, and create interferencewith each other, which reduces performance at many areas of cell edgesresulting in users' devices being in a soft handover state often as usermoves from one small cell coverage area to another—and often all ofthese transitions (handovers) require orchestration back to the corenetwork, further complicating the solution. Add to this the fact that ateach small cell requires backhaul considerations to each devices,typically demanding a dedicated network installed to assure capacity andsecurity—a costly method to deliver. The results from all these factorsis it has relegated small cells to be most suitable in very small officefacilities.

Distributed antenna systems (DAS), in contrast, are exceptional atdelivering balanced signal across medium and larger facilities. UnlikeSmall Cell technology, a DAS acts can either look like a single cell orsmaller number of cells that do not require as many cellular-protocolhandoffs when a user moves from one DAS antenna coverage area toanother. Even when multiple cells are applied the ability to fine tunesignal edges allows the RF design for a building to provide much betteroverall performance for users. They may combine radios with differentpower classes to optimize coverage, can be used to providemultiple-bearer paths to increase performance, and may carry multiplebands across multiple carriers to deliver multi-operator service withinfacilities. Conventionally, they are completely transparent to end userson the system and are dependent on traditional baseband processors(called BBUs or BaseBand Units) and their surrounding controlinfrastructure to “Roam” users from one cell to another. BBUs are thecomponents that carry voice and/or data between a user's cellphone andthe core cellular wireless network (e.g., ATT's network or Verizon'snetwork). In some systems, the BBU may be a component of an eNodeB,which may also include a radio head. Conventional BBUs have no knowledgethat they are on a DAS system, and thus they depend on the DAS to remaintransparent, minimizing any extracurricular delays, and in many aspectsmaintaining its transparency. The conventional DAS and BBU function toprovide capabilities, but they suffer drawbacks and deficiencies becausethey essentially ignore that each other exists.

SUMMARY

Implementations of the present disclosure are directed to a system fordistributing wireless signals in telecommunication networks. The systemcan include a server computer comprising one or more processors and oneor more memory devices. The one or more memory devices storeinstructions that, when executed by the one or more processors, providefunctions of a plurality of baseband units in a mobile network and poolbaseband resources of the plurality of baseband units. The system canalso include a point of interface unit coupled to a distributed antennasystem implementing the mobile network. The distributed antenna systemdistributes signals received from the plurality of baseband units.Additionally, the system can include an interface link coupled to theserver computer and the point of interface unit.

Implementations of the present disclosure are also directed to a methodfor pooling resources in a mobile network and a non-transitory computerreadable medium storing instructions that cause one or more processorsto perform the method. The method can include allocating basebandresources between a plurality of virtual baseband engines supporting themobile network. The method can also include determining a change in ausage of the mobile network. Additionally, the method can includere-allocating, in response to the change in the usage of the mobilenetwork, the baseband resources between the plurality of virtualbaseband engines.

Implementations of the present disclosure are also directed to a methodfor providing network services at a location and a non-transitorycomputer readable medium storing instructions that cause one or moreprocessors to perform the method. The method can include enabling aninterface for providing information associated with a user device. Themethod can also include registering an application with the interface.The application provides one or more services to the user device basedat least partially on the information. Further, the method can includereceiving first information associated with the user device. The firstinformation comprises one or more of identification information of theuser device and state information of the user device. Additionally, themethod can include pushing, via the interface, the first information tothe application.

Implementations of the present disclosure are also directed to a methodfor establishing a mobile call over a wireless network and anon-transitory computer readable medium storing instructions that causeone or more processors to perform the method. The method can includereceiving a request to establish a communication path from a user deviceto a mobile operator network through a wireless access point. The methodcan also include determining whether the user device is authorized toaccess the wireless access point. Further, the method can includesending, in response to the user device being authorized to access thewireless access point, a request to authenticate the user device to themobile operator network. Additionally, the method can includeestablishing, in response to the user device being authorized, thecommunication path from the user device to the mobile operator networkthrough the wireless access point.

Implementations of the present disclosure are also directed to a methodfor aggregating baseband in a local mobile network and a non-transitorycomputer readable medium storing instructions that cause one or moreprocessors to perform the method. The method can include receiving, froma baseband unit in the local mobile network, a request to establishcommunications from a user device to a mobile operator network. Themethod can also include establishing a first communication path to thebaseband unit. Further, the method can include establishing a secondcommunication path to the mobile operator network. Additionally, themethod can include associating the first communication path and thesecond communication path. The method can include receiving, from a newbaseband unit in the local mobile network, a request to establishcommunication path from the user device to the mobile operator network.The method can also include establishing a third communication path tothe new baseband unit and associating the second communication path andthe third communication path.

BRIEF DESCRIPTION OF THE DRAWINGS

Various features of the implementations can be more fully appreciated,as the same become better understood with reference to the followingdetailed description of the implementations when considered inconnection with the accompanying figures, in which:

FIG. 1 is a generic diagram that illustrates an example of a location,which can be provided with integrated network services, according tovarious implementations;

FIG. 2 is a diagram that illustrates a more detailed example of thelocation, which can be provided with integrated network services,according to various implementations;

FIGS. 3A-3E are diagrams that illustrates an example of a local mobilenetwork, according to various implementations;

FIG. 4 and FIGS. 5A-5C illustrate an example of a method for basebandaggregation routing, according to various implementations;

FIG. 6 and FIG. 7 illustrate an example of a method for establishing aconnection through a WAP, according to various implementations;

FIG. 8 and FIGS. 9A and 9B illustrate an example of a method of forproviding services to a location, according to various implementations;

FIG. 10 and FIG. 11 illustrate an example of a method for routingnetwork communications, according to various implementations; and

FIG. 12 illustrates an example of a hardware configuration for acomputer device, according to various implementations.

DETAILED DESCRIPTION

For simplicity and illustrative purposes, the principles of the presentteachings are described by referring mainly to examples of variousimplementations thereof. However, one of ordinary skill in the art wouldreadily recognize that the same principles are equally applicable to,and can be implemented in, all types of information and systems, andthat any such variations do not depart from the true spirit and scope ofthe present teachings. Moreover, in the following detailed description,references are made to the accompanying figures, which illustratespecific examples of various implementations. Electrical, mechanical,logical and structural changes can be made to the examples of thevarious implementations without departing from the spirit and scope ofthe present teachings. The following detailed description is, therefore,not to be taken in a limiting sense and the scope of the presentteachings is defined by the appended claims and their equivalents.

FIG. 1 is a generic diagram that illustrates an example of a location100, which can be provided with integrated network services, accordingto various implementations. While FIG. 1 illustrates various componentscontained in the location 100 and coupled to the location 100, FIG. 1illustrates one example and additional components can be added andexisting components can be removed.

The location 100 may be any type of geographic location, building,house, etc. in which integrated network services can be provided, asdescribed herein. For example, the location 100 can be an officebuilding of a corporation, an apartment building, a multi-dwellingresidence, a government building, a city block, a park etc. The location100 can include a mobile services engine (MSE) 102. The MSE 102 can beconfigured to coordinate, track, and facilitate network communicationsinternal and external for the location 100. The MSE 102 can beconfigured to coordinate, track, and facilitate communications betweennetworks, computer system, user devices, etc. located internally withinthe location 100. Likewise, the MSE 102 can be configured to coordinate,track, and facilitate communications between networks, computer system,user devices, etc. located internally within the location 100 andnetworks, computer system, user devices, etc. located externally fromthe location 100. Additionally, the MSE 102 can provide a set ofapplications programming interfaces (API) for services provided to thelocation 100, for example, from internal application services orexternal application services.

In implementations, the MSE 102 can be implemented as software,hardware, or combination thereof. When implemented as software, the MSE102 can be executed on one or more computer systems, whether virtual,physical, or combinations thereof. For example, physical computersystems can include conventional computer systems, such as those datacenters, servers, etc. The physical computer systems can includehardware resources, such as processors, memory, network hardware,storage devices, and the like, and software resources, such as OS,application programs, and the like. Likewise, for example, the virtualcomputer systems can include virtual machines, cloud computingenvironments, etc. When implemented as software, the MSE 102 can bewritten utilizing a variety of programming languages, such as JAVA, C,C++, Python code, hypertext markup language (HTML), extensible markuplanguage (XML), and the like to accommodate a variety of operatingsystems, computing system architectures, APIs, etc.

The MSE 102 can be configured to provide an interface for and tonegotiate network communications for a local mobile network 104. Thelocal mobile network 104 can include one or more virtual basebandengines (VBEs) 106 and one or more radio frequency (RF) distributionplatforms 108. The local mobile network 104 can provide service to oneor more user devices (UEs) 110 within the location 100. The VBE canprovide one or more baseband units (BBUs) to support and control mobilecommunications with the RF distribution platforms 108. The VBEs 106 canbe implemented a software, hardware, or combination thereof, asdiscussed below. For example, when implemented as software, the VBEs 106can be executed on one or more computer systems, whether virtual,physical, or combinations thereof. For example, physical computersystems can include conventional computer systems, such as servers usedwithin data centers, etc. The physical computer systems can includehardware resources, such as processors, memory, network hardware,storage devices, and the like, and software resources, such as OS,application programs, and the like. Likewise, for example, the virtualcomputer systems can include virtual machines, cloud computingenvironments, etc. When implemented as software, the MSE 102 can bewritten in a variety of programming languages, such JAVA, C, C++, Pythoncode, hypertext markup language (HTML), extensible markup language(XML), and the like to accommodate a variety of operating systems,computing system architectures, etc. The RF distribution platforms 108can be any type of radio/antenna platform such as a distributed antennasystem (DAS), a remote radio head (RRH), and the like. The RFdistribution platforms 108 can be implemented using software, hardware,or combination thereof, as discussed below.

The UEs 110 can be any type of computer systems and devices that arecapable of communicating with the local mobile network 104 and/or anyother network, internal or external, to the location 100. For example,the UEs 110 can include telephones, mobile phones, laptop computer,server computers, tablet computers, smart appliances, IoT devices, andthe like.

In implementations, the VBEs 106 and the RF distributions platforms 108implementing the local mobile network 104 (and/or the MSE 102) canstore, keep track of, and/or otherwise monitor the distribution (e.g.,location) of remote radios and antennas in the RF distributionsplatforms 108, and can identify, monitor, and/or otherwise determine theUEs 110 locations in relation to each radio/antenna of the RFdistributions platforms 108. Using this intelligence information, theVBEs 106 and the RF distributions platforms 108 implementing the localmobile network 104 (and/or the MSE 102) can dynamically optimize theallocation of available BBU resources to best serve the location 100.Because the local mobile network 104 can operate as a finely tuned andsingle system, utilizing one or more wireless technologies and thusmaximizing the end user throughput at any point or points across thesystem.

For example, if location 100 is a venue, such as a football stadium,which is covered by a DAS, the local mobile network 100 can be a singlecell covered by multiple antennas of the DAS. In this example, duringthe second quarter, one of the end-zone sections of the stadium seatingmay be covered by one specific antenna of the multiple DAS antennasthroughout the stadium, and there may be 500 users (e.g., cellphones)being served by that antenna. At the same time, another antenna in aconcourse area of the stadium may be serving 20 users because mostpeople are in their seats and the concourse is lightly occupied. Whenhalftime arrives, most of the users the end-zone section, as well asfrom other sections, may crowd into the formerly lightly occupiedconcourse section, such that the antenna serving the concourse area nowhas 700 users, while the antenna serving the end-zone section now hasonly 50 users because all the others have moved elsewhere. In thisexample, VBEs 106 and the RF distributions platforms 108 implementingthe local mobile network 104 (and/or the MSE 102) can sense a change inuser numbers in the end-zone section antenna and in the concourse-areaantenna, and react by reallocating cellular resources (e.g., BBUresources) from serving the end-zone section antenna to serving theconcourse-area antenna, thus improving the network performance for theusers in the concourse-area. In various implementations, this dynamic,situation-responsive functionality can be achieved by the VBEs 106 andthe RF distributions platforms 108 implementing the local mobile network104 (and/or the MSE 102), which determines where BBU resources areneeded within a venue or other area covered by a local mobile network104 and moves, reassigns, or otherwise reallocates BBU resources to meetthe current needs.

In implementations, the MSE 102 can be configured to provide aninterface for and to negotiate communication between the location 100and one or more external networks 112. The one or more external networks112 can be any type of network that utilizes any type of communicationprotocols or processes. For example, the one or more external networks112 can be mobile carrier networks (also referred to as mobile operatornetwork), Internet Protocol (IP) based network, and the like. The MSE102 can be configured to transparently control and negotiatecommunications between systems and devices and the one or more externalnetworks 112, as discussed further below. The MSE 102 can also beconfigured to provide one or more interfaces, e.g. applicationprogramming interfaces (APIs), to services provided by the one or moreexternal networks 112, as discussed further below.

In implementations, the MSE 102 can be configured to provide aninterface for and to negotiate communications with one or more internalnetworks 114. The one or more internal networks 114 can be any type ofnetwork that utilizes any type of communication protocols or processes.For example, the one or more internal networks 114 can be or includewireless access point (WAPs), trusted local area networks (LANs),untrusted LANs, and the like. The MSE 102 can be configured totransparently control and negotiate communications between systems anddevices and the one or more internal networks 114, as discussed furtherbelow. The MSE 102 can also be configured to provide one or moreinterfaces, e.g. APIs, to services provided by the one or more internalnetworks 114, as discussed further below.

In implementations, the MSE 102 can be configured to provide aninterface for and to negotiate communication with one or moreapplication services 116. For example, the MSE 102 can provide an APIsfor the application services. The application services 116 can be anytype of application, functionality, and the like, which can be utilizedin the location 100, as described below.

For example, as noted above, the VBEs 106 and the RF distributionsplatforms 108 implementing the local mobile network 104 (and/or the MSE102) can store or otherwise keep track of the location of each remoteradio and antenna in the RF distributions platforms 108. In someimplementations, the MSE 102 can use the radio/antenna-locationintelligence information to identify the location of UEs 110 within thearea covered by the local mobile network 104, and employ intelligencethrough other means, such as Wireless Access Point beacons, BluetoothBeacons, to effectively and in combination utilize proximity andtriangulation techniques to achieve user-device location to enablevarious applications, such as user-device map applications that show auser's current location within a venue and provide directions for theuser to follow to arrive at a different location, such as a specificseat, room, meeting, shop, restaurant or the like. Similarly, thedetermined user-device location can be employed by 911 applications toreport the location of the use making a 911 call, or otherwise employedby similar emergency applications. Where and when further enabled byemerging UE standards a 911 call by a user or other emergency statewithin a location may allow for the MSE and/or VBEs to force anemergency state of the UE, enabling all radios in the UE device,including cellular, Wi-Fi, and Bluetooth technologies, to optimizelocation intelligence to the benefit of users in an emergency state.

In implementations, the VBEs 106 and the RF distributions platforms 108implementing the local mobile network 104 (and/or the MSE 102) areconfigured to provide solutions targeted at a location 100, such ascorporate centers or university campuses, that have the ability to roamUEs 110 onto and within the location 100. In some embodiments, the VBEs106 and the RF distributions platforms 108 implementing the local mobilenetwork 104 (and/or the MSE 102) can handover the UEs 110 using standardinter-RAT and intra-RAT handoff methodologies to enable transparenttransitions into and out of serving areas, including to legacy networksoutside of the pseudo-private system. As a result, the VBEs 106 and theRF distributions platforms 108 implementing the local mobile network 104(and/or the MSE 102) allows secure access to local private IP networksthat may be affiliated with the location 100.

In some implementations, the VBEs 106 and the RF distributions platforms108 implementing the local mobile network 104 (and/or the MSE 102) canintelligently identify qualified UEs to utilize the networks and systemsof the location 100, whereby the VBE 106 (and/or MSE 102) may optionallyimplement a Closed Subscriber Group, which shall limit which UEs areallowed to handover to the location 100 based on policies set forth by aconfiguration of the system, and can also apply special data routingpolicies to individual UEs 110 to enable users to access variousnetworks and data resources of the location 100, such as: the internet,the operator's IP-core network for things such as high definition voiceand video calls or IP Multimedia Subsystem (IMS) services, or local IPnetwork to the location 100, such as internal file stores, databases,and other tools accessible via a secure connection to UEs 110. Forexample, consider a venue such a corporate campus that is served by animplementation of location 100. In such a venue, it may be desirable toenable employees of the corporation to connect to and access data in thecorporation's computers or intranet, while denying such connectivity andaccess to visitors on the campus who are not corporate employees. Inthis example, the system may identify the UEs 110 of corporate employeesthat connect via cellular means to the local mobile network 104, andallow those UEs 110 to access the corporation's computers according tothe routing policies for corporate employees. Similarly, the system mayidentify the UEs 110 of visitors (i.e., non-corporate employees) thatconnect via local mobile network 104, and prevent those UEs 110 fromaccessing the corporation's computers. In addition to access rights, thepolicy may also specify other features or resources to supply or deny toUEs 110, such as an amount of bandwidth, fees for access, and the like.

In some implementations, the special data routing policies may allowaccess to industrial, Internet of Things (IoT), and Machine to Machine(M2M) environments. For example, the VBEs 106 and the RF distributionsplatforms 108 implementing the local mobile network 104 (and/or the MSE102) can provide various communication functions and utility, such asallowing LTE-modem-embedded shipping pallets with localized radiofrequency identification (RFID) tagging, which identifies the items onthe pallet, to connect and communicate to internal systems as thepallets move through a factory and into shipping trucks.

While FIG. 1. illustrates one MSE 102, the location 100 can includemultiple instances of the MSE 102. For example, multiple instances ofthe MSE 102 to communicate with different local mobile networks 104,different external networks 112, different internal networks 114,different application services 116, and the like.

FIG. 2 is a diagram that illustrates a more detailed example of thelocation 100, which can be provided with integrated network services,according to various implementations. While FIG. 2 illustrates variouscomponents contained in the location 100 and coupled to the location100, FIG. 2 illustrates one example and additional components can beadded and existing components can be removed.

As illustrated in FIG. 2, the local mobile network 104 can include a DAS202 coupled to the VBEs 106. For example, the VBEs 106 can be coupled tothe DAS 202 via a digital interface, such as a common public radiointerface (CPRI) interface 204.

The local mobile network 104 can include one or more additional smallcell systems 206 coupled the VBEs 106. For example, small cell systems206 can include existing hardware such as donor antennas, EnodeB's,small cells, and the like as additional RF sources as well asincorporating the BBU (VBEs 106) technology, for example. Inputs fromthese devices can be 2G, 3G, 4G, public safety, etc. radio frequency andare agnostic to the carrier frequency, manufacturer and/or type ofequipment. Accordingly, the local mobile network 104 may utilizeexisting network infrastructure to IP-based, managed systems, e.g.,while continuing to capitalize on at least some previously-implementedhardware, software, etc.

The VBEs 106 can be configured to coordinate and control mobilecommunication with the local mobile network 104. The VBEs 106 can gatherintelligence information about the DAS 202 usage by users and thecurrent system resources (e.g., BBU resources), and use thatintelligence information to reallocate system resources to better servethe current users, for example, UEs. The intelligence information caninclude information regarding the identity, service capabilities for(e.g., type of device, its LTE capabilities, ability to offer Voice overLTE, multi-path radio capabilities, etc.), and location of userequipment (e.g., smartphones or IoT devices) and user-equipment sessionsthat are wirelessly connected to (e.g., roamed onto) the DAS 202 andeach specific sub-element of the DAS 202 (e.g., each antenna, remoteradio unit, coverage area, and the like). The VBEs 106 can collect andstore information about the amount, capacity, and current allocation ofBBU resources, across pools of BBU processors, which may be rack units,and have knowledge of available baseband frequencies, frequency bands,power output, bandwidth, sessions, channels, processing cycles or time,digital signal processing capacity, registered and active users ordevices, device types, and the like.

The location 100 includes a switch 207, whereby such switch may be anexternally programmable device or an integral element of the MSE. Forexample, the switch 207 can be an independent software definednetworking (SDN) switch. The switch 207 can be dynamically configured bythe MSE to setup certain packet level routing paths for networkcommunication between systems and devices within the location 100, forexample, the local mobile network 106, a local area network 212, andwireless access points (WAPs) 214, and networks external to the location100, for example, internet service provider (ISP) networks 208 andmobile carrier networks 210.

In implementations, the MSE 102 can be configured to communicate withthe VBEs 106 and a switch or switches 207. The MSE 102 can be configuredto transparently negotiate and control the network communication handledby the VBEs 106 and the switch 207 as discussed further below.Additionally, the MSE 102 can be configured to collect, store, andutilize data and intelligence information from the VBEs 106.

In implementations, the MSE 102 can be configured to include a networkfunctions virtualization (NFV) interface 216. For example, the NFVinterface 216 can be one or more APIs that enable functionality of oneor more NFV proxies and/or middleware 218. In some implementations, theNFV interface 216 can be utilized by the MSE 102 and the NFV proxies andmiddleware 218 to implement evolved packet core (EPC) functions 220, forcommunication over network standards, such as 3GPP LTE wirelesscommunication standard. For example, the EPC functions 220 can includecertain information for the registration and policies of UEs, mobilehandoff coordination of UEs, authentication of UEs, certain servicesenabled or allowed by a UE and related policies to be applied, packetredirection internally, externally, or both for location 100, and thelike. The MSE 102 can be configured to implement and communicate via theNFV interface 216 using any type of protocol, for example, JAVA scriptobject notation (JSON), XML, and the like.

In implementations, the MSE 102 can be configured to include anenterprise function virtualization (EFV) interface 222. For example, theEFV interface 222 can be one or more APIs that enable functionality ofone or more EFV middleware 224 and one or more enterprise application226. In some implementations, the EFV interface 222 can be utilized bythe MSE 102, EFV middleware 224, and enterprise application 226 toimplement application services within the location 100, as discussedfurther below. For example, the application services can include packetredirection internally, externally, or both for location 100, policycontrol for the location 100, emergency services for the location 100,enhance user experience at location 100, and the like. The MSE 102 canbe configured to implement and communicate via the EFV interface 222using any type of protocol, for example, JAVA script object notation(JSON), XML, and the like.

FIGS. 3A-3E are diagrams that illustrates an example of the local mobilenetwork, for example local mobile network 104, according to variousimplementations. While FIGS. 3A-3E illustrate various componentscontained in the local mobile network and coupled to the local mobilenetwork, FIGS. 3A-3E illustrate one example and additional componentscan be added and existing components can be removed.

As illustrated in FIG. 3A, globally indicated with reference number 301is a system for the distribution of wireless signals intelecommunication networks, for example, the local mobile network 106 inthe location 100, particularly for providing a baseband unit (BBU)functionally integrated with a distributed antenna system (DAS). In someimplementations, the system 301 can provide greater flexibility,modularity and future-proof architectures, by implementing the followingfeatures:

integration into the system 301 of the functionality for the generationof the signal to be distributed;

realization of communication links, for example, propriety opticallinks, based on a high speed CPRI or Ethernet standard;

integration into the system 301 of all existing technologies (2G, 3G,4G), by creating a framework that can handle even future technologies(5G).

In this way, the system 301 can provide a solution for the realizationof the base stations that are innovative from the economic point of view(cost reduction and economies of scale), from an engineering point ofview (computational and dynamic utilization efficiency) and from theenvironmental point of view (efficiency and energy saving).

As shown schematically in FIG. 3A, the system 301 includes two blocks302 and 303 closed in the dotted rectangle and related to the basestation BTS (or BBU or eNodeB depending on the technology used, i.e.,2G, 3G, 4G) and the Point Of Interface (POI) of a DAS system. In someexamples, the system 301 can be easily integrated into the conventionalstructures of a DAS. In some implementations, the system 301 can bepartially integrated with the DAS and operatively connected with theconventional master unit 304 of the DAS itself. The master unit 304 canbe connected through an optical fiber connection to a remote unit 305.The master unit 304 can perform an RF-to-optical conversion and viceversa, while the remote unit 305 can perform signal amplification andoptical-to-RF conversion and vice versa. The remote unit 305 can befurther connected to a distributed antenna system 306 for thedistribution of signals.

FIGS. 3B and 3C are block diagrams that illustrate an example of thearchitecture of the system 301. As illustrated, the system 301 providesan architecture composed of the following components:

one or more central server 307 provided with one or more a baseband unit308 (BBU) via VBEs, for example, implemented with BBU pooling software309;

one or more point of interface units 310 connected with a DAS todistribute the signal received from the baseband unit 308 in areas, forexample, areas with high density of users; and

one or more an interface links 311 connected with the central server 307and with said the one or more point of interface units 310.

For example, the system 301 includes a point of interface network 312provided with a plurality of the point of interface units 310 thatinterface with the central server 307 via the interface links 311 andwhich is connected with the DAS to distribute the signal received fromthe BBU 308 in areas, for example, areas with high density of users.

The interface link 311 includes a plurality of optical connecting links.The communication through the connecting links 311 can be implemented bymeans of protocol of the CPRI and/or Ethernet type. The system 301comprises a plurality of BBU 308 realized via a BBU pooling software 309configured on the central server 307.

The system 301 provides the possibility to realize on the central server307 a set of BBU 308, called BBU-pool. The BBU pooling software 39 forthe implementation of the BBU-pool can be, for example, a type of asoftware radio. The central server 307 can be, for example, one or morephysical computer systems or virtual computer systems, as discussedabove. In some implementations, the number of BBUs 308 implemented onthe central server 307 can depend on the number of processors of thecomputer on the central server 307, itself. The central server 307 ofthe system 301 can include one or more electronic connection cards 313and one or more digital CPRI links (or an Ethernet links) between theBBU-pool 308 and the electronic connection cards. In someimplementations, the electronic connection card 313 can be a PCI card.

The electronic connection card 313 can be equipped with an FieldProgrammable Gate Array (FPGA) chip 314 capable of ensuring highperformance (in terms of clock rates used, power consumption, etc.) Theelectronic connection card 313 can include one or more CPRI links 315(or an Ethernet links). The CPRI links 315 perform thetransmission/reception on fiber of the base band signal and implementsthe merging of CPRI and Ethernet data.

For example, the electronic connection card 313 can be provided withfour CPRI links 315 (or Ethernet links) connected to correspondingoptical connecting links 311. While illustrated with four links, theelectronic connection card 313 can include more than four CPRI links315. In some implementations, the CPRI links 315 on the electronicconnection card 313 can be a type of CPRI Master links.

The BBU-pooling software 309 interfaces with the electronic connectioncard 313 through an interface unit 316, for example, a PCI Expressinterface, and with supervision software 317 that acts as supervision ofcentral server 307 and POI-Network 312.

The connecting links 311 connect the electronic connection card 313 ofthe central server 307 with the point of interface unit 310 of the DAS.In some implementations, the point of interface units 310 can beimplemented by means of dedicated POI-CPRI boards. In someimplementations, the connecting links 311 are constituted by high-speedoptical links with CPRI/Ethernet protocol.

The POI-CPRI boards 310 are implemented using FPGA boards 318, whichallow both the management of the connecting links 311, both theimplementation of re-programmable and re-configurable circuitry, such asdigital filtering and adaptive modulation/demodulation of the signal. Insome implementations, the POI-Network 312 can consist of severalPOI-CPRI boards 310 equipped with a plurality of ports 319 connected torespective connecting links 311. The POI-CPRI boards 310 can be equippedalso with a plurality of ports 320 connected to respective connectinglinks 311.

In some implementations, the POI-CPRI boards 310 can be provided withCPRI slave interfaces and CPRI master interfaces. As shown in FIG. 3,the POI-CPRI boards 310 can be connected to the PCI card 313 throughCPRI Slave interfaces and are also interconnected each other throughCPRI Master/Slave interfaces. The type of the POI CPRI/Ethernet links ofthe POI-CPRI boards 310 can be dynamically reconfigurable as a functionof the fact that they must be of Master or Slave type. This makes itpossible to create a fully interconnected network between the variousPOI-CPRI boards 310 which has advantages in terms of routing,sustainability and redundancy of the connecting links 311 in case ofmalfunctions/loss of one or more links.

The BBU pooling software 309 can realizes the virtualization of theBBU-pool 308 or eNodeB (eNB) system. In this way the BBU-pool 308 (oreNB) can be hardware independent (it does not require a dedicatedhardware) but it can be installed on server machine scalable in terms ofCPU power. For example, depending on CPU power, the BBU pooling is ableto manage from one to tens of LTE 20 MHz MIMO 2×2 carriers. The BBUpooling software 309 can be configured, managed and monitored via asupervision software 317 that realizes the OMT (Operational andMaintenance Terminal) via a web based GUI and via a BBU maintenancenetwork 321. With the same web based GUI it can be possible toconfigure, manage and monitor the POI-CPRI boards 310 up to the DASplatform interface. In some implementations, the DAS platform itself canbe managed by a similar but separated web GUI to keep BBU-pool 308 andDAS platform independently manageable.

In some implementations, through OMT web pages, it is possible to managethe LTE datastream coming from operator backhaul network 322 to the I/Qdrivers and from I/Q drivers to distribute the LTE data to thedestination POI-CPRI boards 310 through connecting links 311. In thisway, on each POI-CPRI board 310, it is possible to generate the RFsignal related to the desired band and sector, then this signal willdrive the DAS. This platform is flexible, fully configurable andperfectly fits the multiband/multioperator DAS platform.

Concerning the electronic connection card 313, it is preferablyconstituted by a FPGA card 314. For example, the electronic connectioncard 313 can be constituted by a software reprogrammable circuitryinserted within the central server 307 through a PCI Express interface316 of the latest generation. The electronic connection card 313 packsthe stream of base-band data generated by the BBU pooling software 309and received via the PCI Express interface 316, according to theCPRI/Ethernet standards, in order to interface to the POI-CPRI boards310 of the POI-Network 312.

A more detailed diagram of the circuitry implemented on the electronicconnection card 313, for example, a PCI Card, is shown in FIG. 3D. TheFPGA board 314 implement a PCI-Express communication interface 323.Furthermore, the FPGA board 314 comprises a memory management unit 324of the Direct Memory Access (DMA) type for managing memory accessesto/from the central server 307 memory and from/to the memory on the FPGAboard 314.

The FPGA board 314 further includes custom interfaces to align theformat of the three different data interfaces and PCIe, DMA and CPRI,and other custom algorithms of signal processing to organize, optimizeand tailored stream of data with respect to the POI-Network 312. TheFPGA board 314 also comprises organization units 326 for organizing dataaccording to the CPRI standard. In some implementations, theorganization units 326 performs AxC IQ data mapping, interleaving frameand synchronization management.

An example of a hardware architecture of a POI-CPRI Board 310 is shownin detail in FIG. 3E. The POI-CPRI board 310 can include the followingcomponents:

four SFP+ ports 319 for the four CPRI link;

two 1-Gigabit Ethernet ports 320, one to provide a Wi-Fi type access byconnecting an access-point and the other as a local Ethernet port formaintenance and debugging;

components and circuitry for signal transmission in the Downlink pathand Uplink path, including blocks 327 for the analog/digital conversionand digital/analog conversion, blocks 328 for filtering, IF/RFmodulators 329, attenuators 330, amplifiers 331, RF synthesizer 332,flash memory 333, DDR memory 334, oscillators 335 and a Clockdistributor 336; and

an FPGA board 318 with integrated hardware microprocessors.

The FPGA board 318 can perform the following functions:

digital signal reception/transmission from the A/D converter and to theD/A converter;

digital signal reception/transmission from CPRI Slave/Master interfaces;

Master/Slave configuration of CPRI interfaces;

routing from/to CPRI interface of the signal and of the Ethernet linkencapsulated in the CPRI;

programming of all the circuitry of the board;

digital filtering;

conversion from intermediate frequency to base-band and from base-bandto intermediate frequency;

various algorithms of signal processing;

monitoring the functioning of all the devices mounted on the board;

automatic alarm management; and

communication via Ethernet encapsulated in the CPRI links with thesupervision of the Central Server software routines.

The realization of the BBUs in software on the central server allows:cost savings for production operators; savings production materials andphysical dimensions apparatus; energy saving; intercommunication betweenmultiple BBU; and use of a FPGA board for the management of the CPRIlink high speed. Furthermore, the realization of the specific digitaland interconnected CPRI-POI boards allows: the communication between thevarious boards with optical CPRI links; the ability to reroute trafficdynamically; and high flexibility and re-configurability of the POInetwork; and re-programmability of the individual CPRI-POI board throughthe use of FPGA boards.

Because the integrated BBU/DAS system operates as a finely tuned andsingle system, it can minimize the disadvantageous of consistentsoft-handover states that typically occur in when users are traversingacross numerous small cells, while maximizing the end user throughput atany point or points across the system. The integrated BBU/DAS systemallows to store, keep track of, and/or otherwise monitor thedistribution of remote radios and antennas in the DAS, and may identify,monitor, and/or otherwise determine the end users' (e.g., cellphones)localizations in relation to each DAS radio/antenna. Using thisintelligence information, the system can dynamically optimize theallocation of available BBU resources to best serve the locations ofthese different user communities.

FIG. 4 and FIGS. 5A-5C illustrate an example of a method 400 forbaseband aggregation routing, according to various implementations. Theillustrated stages of the method are examples and that any of theillustrated stages can be removed, additional stages can be added, andthe order of the illustrated stages can be changed.

In 402, a UE roams into a first area of a location. For example, asillustrated in FIG. 5A, a UE 502 can be receiving mobile services from amobile operator network 504 via an external “macro” cell 506. The UE 502can enter a first area 508 of the location 100. For example, thelocation 100 can be an office building and the first area 508 can be thelobby of the office building.

In 404, the UE locates a baseband unit. For example, as illustrated inFIG. 5A, once the UE 502 enters the first area 508, the UE 502 candetect a radio signal from a RF unit 510 coupled to the one or more ofthe VBEs 106. For instance, the UE 502 can activate a search for a radiosignal. Once the UE 502 enters the area 508, the UE 502 can detect theradio signal from the RF unit 510 and attempt to establish a connectionwith a baseband unit of the VBEs 106.

In 406, the baseband unit establishes a communication path with the UE.For example, the baseband unit of the VBEs 106 can authenticate the UE502 and register the UE 502 with the VBEs 106. The VBEs 106 canauthenticate the UE 502 with the mobile operator network 504 via the MSE102. As illustrated in FIG. 5B, once the UE 502 has been authenticated,the VBEs 106 can establish a communication path 516 with the UE 502. Thecommunication path 516 can be any type of mobile communication path orsession. For example, the communication path 516 can be a 3GPP LTEwireless communication which includes three tunnels, e.g., voice, data,and control.

In 408, the MSE establishes a communication path with the baseband unit.For example, as illustrated FIG. 5B, the MSE 102 can establish acommunication path 518 with the VBEs 106. The communication path 518 canbe the same type of communication path as communication path 516. In410, the MSE 102 establishes a communication path with an externalnetwork. For example, as illustrated FIG. 5B, the MSE 102 can establisha communication path 520 with the mobile carrier network 504. Thecommunication path 520 can be the same type of communication path ascommunication path 516 and 518. In 412, the MSE associates thecommunication path with the external network and the communication pathwith the baseband unit. In implementations, the MSE 102 operates incoordination with VBEs 106 to establish the complete communication pathto the mobile carrier network 504 in near-real time. Additionally, theMSE 102 can operate transparently so that the UE 502 and the mobilecarrier network 504 appear to make a normal mobile connection.

In 414, the UE may roam into a second area of the location. For example,as illustrated in FIG. 5C, the UE 502 can roam into a second area 512 ofthe location 100, for instance, a different room or floor of thelocation 100.

In 416, the UE locates a new baseband unit. For example, once the UE 502enters the second area 512, the UE 502 can detect a radio signal from aRF unit 514 coupled to the one or more of the VBEs 106. For instance,the UE 502 can activate a search for a radio signal. Once the UE 502enters the second area 512, the UE 502 can detect the radio signal fromthe RF unit 512 and attempt to establish a connection with a newbaseband unit of the VBEs 106.

In 418, the new baseband unit establishes a communication path with UE.For example, the baseband unit of the VBEs 106 can authenticate the UE502 and register the UE 502 with the VBEs 106. The VBEs 106 canauthenticate the UE 502 with the mobile operator network 504 via the MSE102. Likewise, the original baseband unit can hand over the UE 502 tothe new baseband unit using a protocol such as X2. As illustrated inFIG. 5B, once the UE 502 has been registered, the VBEs 106 can establisha communication path 522 with the UE 502.

In 420, the MSE establishes a communication path with the new basebandunit. For example, as illustrated FIG. 5C, the MSE 102 can establish acommunication path 524 with the VBEs 106. The communication path 524 canbe the same type of communication path as communication path 522.

In 422, the MSE associates the existing communication path with theexternal network with the communication path with the new baseband unit.For example, the MSE 102 can associate the existing communication path520 with the communication paths 522 and 524. In implementations, theMSE 102 operates in coordination with VBEs 106 to establish the completecommunication path to the mobile carrier network 504 in near-real time.Additionally, the MSE 102 can operate transparently so that the UE 502and the mobile carrier network 504 appear to make a normal mobileconnection.

FIG. 6 and FIG. 7 illustrate an example of a method 600 for establishinga connection through a WAP, according to various implementations. Theillustrated stages of the method are examples and that any of theillustrated stages can be removed, additional stages can be added, andthe order of the illustrated stages can be changed.

In 602, the MSE receives a request to establish a communication paththrough a WAP. For example, as illustrated in FIG. 7, a UE 702 can be inlocation 100 and can send a request to establish a communication paththrough a WAP 704 to a mobile operator network 706. The UE 702 cancommunicate with the WAP 704 using any type of wireless communicationprotocol. The communication path can be any type of communication path,for example, voice over IP.

In 604, the MSE determines whether the WAP is subject to an accesspolicy. For example, the location 100 may allow only certain definedgroups of UEs to access the WAP 704. To determine policy compliance, theMSE 102 can include a policy engine 708. The policy engine 708 can beconfigured to determine whether the WAP 704 is subject to a policy andto determine the appropriate policy manager to check. For example, thepolicy engine 708 can maintain a record of WAPs subject to policymanagement and can compare identification information for the WAP 704 tothe record.

If the WAP is subject to policy management, in 606, the MSE determineswhether the policy is governed by a local or external policy manager.For example, as illustrated in FIG. 7, the MSE 102 may provide the EFVinterface 222 to a local policy manager 710 and a external policymanager 712.

If the policy is governed by a local policy manager, in 608, the MSEsends a policy check request to the local policy manager. For example,the MSE 102 can send a policy check request to the local policy manager710 via the EFV interface 222. The policy check request can includeinformation that identifies the UE 702 and the WAP 704.

If the policy is governed by an external policy manager, in 610, the MSEsends a policy check request to the external policy manager. Forexample, the MSE 102 can send a policy check request to the externalpolicy manager 712 via the EFV interface 222. The policy check requestcan include information that identifies the UE 702 and the WAP 704.

In 612, the MSE determines whether the UE can access the WAP. Forexample, the MSE 102 can receive a response from the local policymanager 710 or the external policy manager 712 that indicates whetherthe UE 702 can access the WAP 704.

If the UE is authorized, the MSE sends a request for authentication ofthe UE from the mobile carrier network. For example, as illustrated inFIG. 7, the MSE 102 can send a request to a home subscriber server (HSS)714. The request can include an identification of the UE 702, forexample, an identification of a SIM card of the UE 702. The MSE 102 cansend the request via an interface, for example, the NFV interface 216.The HSS 714 can communicate with a subscriber database 716 to determinewhether to authenticate the UE 702.

In 616, the MSE determines whether the UE is authenticated to aces themobile carrier network. For example, the MSE 102 can receive a responsefrom the HSS 714 that indicates whether the UE 702 can access the mobilecarrier network 706. The response can also indicate that the UE 702 canestablish a connection path through the WAP 704.

If the UE is authenticated, in 618, the MSE establishes a communicationpath to the mobile carrier network. For example, the MSE 102 canestablish a communication path 718 through the WAP 704.

FIG. 8 and FIGS. 9A and 9B illustrate an example of a method of 800 forproviding services to a location, according to various implementations.The illustrated stages of the method are examples and that any of theillustrated stages can be removed, additional stages can be added, andthe order of the illustrated stages can be changed.

In 802, the MSE enables an interface for application services. Forexample, the MSE can configure the interface to be accessible byapplications, for example, configure the interface to enable access tothe protocols associated with the application. In 804, the MSE registersand authenticates an application with the interface. For example, theapplication utilizes an authentication exchange using an XML, JSON, orother interface to process the authentication exchange and possibleutilizing certification key methods, to validate that the application isa valid application and should be allowed access to the interface forapplication services.

In 806, the MSE receives information associated with a UE, which may bea mobile phone user or other non-user devices that may be on thisnetwork such as IoT devices. The information associated with the UE caninclude any information that allows the MSE to cooperate with theapplication to deliver the services. For example, the information caninclude an identification of the UE, for example, a phone number, a SIMcard identifier, a Media Access Control Address (MAC), etc., and stateinformation for the UE, for example, location of the UE, call status ofa UE, etc. The information can also include a change in the sateinformation for the UE.

In 808, the MSE pushes, via the interface, the information to theapplication. The application can utilize the information to perform theservices provided by the application. In 810, the MSE receives, via theinterface, a request to perform an action from the application. Forexample, based on the information provided, the application can instructthe MSE to perform an action at the location associated with theservices. In 812, the MSE performs the requested action. After 812, themethod 300 can return to 806 and the MSE can await new informationassociated with the UE.

For example, as illustrated in FIG. 9A, the location 100 can be a hotel.The hotel may desire to provide several services to guests of the hotel.For example, the hotel may support automatic check-in and simultaneousroom ringing for a UE 902. In automatic check-in, the location 100 caninclude a hotel property management application 904 that communicateswith the MSE 102 via the EFV interface 222. When the UE 902 enters thehotel, the UE 902 can communicate with the MSE 102, and the MSE 102 caninformation associated with the UE 902, for example, identifyinginformation, location etc. The MSE 102 can then forward the informationtot the hotel property management application 904, via the EFV interface222. In response, the hotel property management application 904 canperform actions, such as identify the user associated with the UE 902,check the user into a room 906 in the hotel, etc. The hotel propertymanagement application 904 can also request that the MSE 102 performactions such as notify the UE 902 of check-in.

In this example, the location 100 may also include a telephone system908. The telephone system 908 can support simultaneous ringing a phone910 when the user is located in their room 906. In this case, the MSE102 can, upon observing an inbound call towards a UE associated with aknown room, and when the UE 902 is identified as being “in the room”906, utilize the EFV interface 222, via a local telephone IP interface,to ring the telephone 910. The MSE 102 can also coordinate routing theincoming call to the telephone 910, if the user answers the telephone910, systematically performing appropriate CODEC translation to matchwith the telephone system 908.

In another example, as illustrated in FIG. 9B, the location of a UE 950can be employed by 911 applications to report the location, for example,a room 952, of the UE 950 making a 911 call, or otherwise employed bysimilar emergency applications. In this example, the MSE 102 can enablean interface for a public safety answering point (PSAP) system 954. Whenthe UE 950 dial 911, the MSE 102 can push the location information ofthe UE 950 to the PSAP system 954. Where and when further enabled byemerging UE standards a 911 call by a user or other emergency statewithin a location may allow for the MSE and/or VBEs to force anemergency state of the UE, enabling all radios in the UE device,including cellular, Wi-Fi, and Bluetooth technologies, to optimizelocation intelligence to the benefit of users in an emergency state.

FIG. 10 and FIG. 11 illustrate an example of a method 1000 for routingnetwork communications, according to various implementations. Theillustrated stages of the method are examples and that any of theillustrated stages can be removed, additional stages can be added, andthe order of the illustrated stages can be changed.

In 1002, the MSE identifies a UE present in a location. The MSE canidentify the UE is present when the UE attempts to communicate with oneof the networks coordinated by the MSE. For example, as illustrated inFIG. 11, a UE 1102 may enter the location 100 and register with the VBEs106.

Once the UE is identified, in 1004, the MSE can determine whether alocal gateway is present. A local gateway can be a system that providesa dedicated bearer channel to certain UEs. For example, a mobileoperator network can offer the dedicated bearer channel as a service tosubscribing UEs. As illustrated in FIG. 11, for example, a local gateway1104 can be offered by a mobile operator network 1106. The local gateway1104 can be implemented in the switch 207. The local gateway 1104 can beimplemented in hardware, software, or combination thereof. The MSE 102can push a request to the mobile operator network 1106 via the NFVinterface 216 to determine if the local gateway 1104 is present. The MSE102 can also examine the switch 207 or records to determine if the localgateway 1104 is present.

If a local gateway is present, in 1006, the MSE determines whether theUE is authorized to use the local gateway. The MSE can communicate withthe mobile operator network associated with local gateway to determineif the UE is authorized to use the local gateway. For example, the MSE102 can push a request to the mobile operator network 1106 via the NFVinterface 216 to determine if the UE 1102 is authorized.

If the UE is authorized to use the local gateway, in 1008, the MSEdirects all packets to the local gateway. For example, as illustrated inFIG. 11, the MSE 102 can establish a communication path 1108 to thelocal gateway.

If a local gateway is not present or the UE is not authorized to use thelocal gateway, in 1010, the MSE inspects packets flowing from the UE andidentifies the destination of the packets. In some implementations, thepackets may be destined for an internal network to the location. Forexample, as illustrated in FIG. 11, the UE 1102 can make a call to asecond UE 1110 that is communicating via a WAP 214, for example, one atrusted or secure network. In 1012, the MSE can validate the UE accessto the secured/trusted network. For example, the MSE 102 can requestvalidation for internal or external policy managers to determine if theUE 1102 can access the secured/trusted network.

In 1014, the MSE identifies priority packets and sets packet flags forthe priority packets. For example, the MSE 102 can determine that thepackets are associated with a voice call. In response, the MSE 102 canset packet flags the packets to identify the packets as priority packetsto receive, for example, special processing, higher quality of service,etc. In 1016, the MSE sets route tables for packets with localdestination. The MSE can set the route tables in the switch 207. Oncethe MSE sets the route tables, the switch 207 can direct traffic to theUE 1110 over the WAP 214.

The foregoing description is illustrative, and variations inconfiguration and implementation can occur to persons skilled in theart. For instance, the various illustrative logics, logical blocks,modules, and circuits described in connection with the embodimentsdisclosed herein can be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor canbe a microprocessor, but, in the alternative, the processor can be anyconventional processor, controller, microcontroller, or state machine. Aprocessor can also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

In implementations, the functions described can be implemented inhardware, software, firmware, or any combination thereof. For a softwareimplementation, the techniques described herein can be implemented withmodules (e.g., procedures, functions, subprograms, programs, routines,subroutines, modules, software packages, classes, and so on) thatperform the functions described herein. A module can be coupled toanother module or a hardware circuit by passing and/or receivinginformation, data, arguments, parameters, or memory contents.Information, arguments, parameters, data, or the like can be passed,forwarded, or transmitted using any suitable means including memorysharing, message passing, token passing, network transmission, and thelike. The software codes can be stored in memory units and executed byprocessors. The memory unit can be implemented within the processor orexternal to the processor, in which case it can be communicativelycoupled to the processor via various means as is known in the art.

For example, FIG. 12 illustrates an example of a hardware configurationfor a computer device 1200 that can be used as a computer system ordevice, which can be used to perform one or more of the processesdescribed above. While FIG. 12 illustrates various components containedin the computer device 1200, FIG. 12 illustrates one example of acomputer device and additional components can be added and existingcomponents can be removed.

The computer device 1200 can be any type of computer devices, such asdesktops, laptops, servers, etc., or mobile devices, such as smarttelephones, tablet computers, cellular telephones, personal digitalassistants, etc. As illustrated in FIG. 12, the computer device 1200 caninclude one or more processors 1202 of varying core configurations andclock frequencies. The computer device 1200 can also include one or morememory devices 1204 that serve as a main memory during the operation ofthe computer device 1200. For example, during operation, a copy of thesoftware that supports the methods and processes described above, forexample, the MSE 102, can be stored in the one or more memory devices1204. The computer device 1200 can also include one or more peripheralinterfaces 1206, such as keyboards, mice, touchpads, computer screens,touchscreens, etc., for enabling human interaction with and manipulationof the computer device 1200.

The computer device 1200 can also include one or more network interfaces1208 for communicating via one or more networks, such as Ethernetadapters, wireless transceivers, or serial network components, forcommunicating over wired or wireless media using protocols. The computerdevice 1200 can also include one or more storage device 1210 of varyingphysical dimensions and storage capacities, such as flash drives, harddrives, random access memory, etc., for storing data, such as images,files, and program instructions for execution by the one or moreprocessors 1202.

Additionally, the computer device 1200 can include one or more softwareprograms 1212 that enable the functionality described above. The one ormore software programs 1212 can include instructions that cause the oneor more processors 1202 to perform the processes and methods describedherein. Copies of the one or more software programs 1212 can be storedin the one or more memory devices 1204 and/or on in the one or morestorage devices 1210. Likewise, the data utilized by one or moresoftware programs 1212 can be stored in the one or more memory devices1204 and/or on in the one or more storage devices 1210.

In implementations, the computer device 1200 can communicate with otherdevices via one or more networks. The other devices can be any types ofdevices as described above. The one or more networks can be any type ofnetwork, such as a local area network, a wide-area network, a virtualprivate network, the Internet, an intranet, an extranet, a publicswitched telephone network, an infrared network, a wireless network, andany combination thereof. The one or more networks can supportcommunications using any of a variety of commercially-availableprotocols, such as TCP/IP, UDP, OSI, FTP, UPnP, NFS, CIFS, AppleTalk,and the like. The one or more networks can be, for example, a local areanetwork, a wide-area network, a virtual private network, the Internet,an intranet, an extranet, a public switched telephone network, aninfrared network, a wireless network, and any combination thereof.

The computer device 1200 can include a variety of data stores and othermemory and storage media as discussed above. These can reside in avariety of locations, such as on a storage medium local to (and/orresident in) one or more of the computers or remote from any or all ofthe computers across the network. In some implementations, informationcan reside in a storage-area network (“SAN”) familiar to those skilledin the art. Similarly, any necessary files for performing the functionsattributed to the computers, servers, or other network devices may bestored locally and/or remotely, as appropriate.

In implementations, the components of the computer device 1200 asdescribed above need not be enclosed within a single enclosure or evenlocated in close proximity to one another. Those skilled in the art willappreciate that the above-described componentry are examples only, asthe computer device 1200 can include any type of hardware componentry,including any necessary accompanying firmware or software, forperforming the disclosed implementations. The computer device 1200 canalso be implemented in part or in whole by electronic circuit componentsor processors, such as application-specific integrated circuits (ASICs)or field-programmable gate arrays (FPGAs).

If implemented in software, the functions can be stored on ortransmitted over a computer-readable medium as one or more instructionsor code. Computer-readable media includes both tangible, non-transitorycomputer storage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media can be any available tangible, non-transitory media thatcan be accessed by a computer. By way of example, and not limitation,such tangible, non-transitory computer-readable media can comprise RAM,ROM, flash memory, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium that can be used to carry or store desired program code in theform of instructions or data structures and that can be accessed by acomputer. Disk and disc, as used herein, includes CD, laser disc,optical disc, DVD, floppy disk and Blu-ray disc where disks usuallyreproduce data magnetically, while discs reproduce data optically withlasers. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Combinations of the above should also be included within the scope ofcomputer-readable media.

While the teachings have been described with reference to examples ofthe implementations thereof, those skilled in the art will be able tomake various modifications to the described implementations withoutdeparting from the true spirit and scope. The terms and descriptionsused herein are set forth by way of illustration only and are not meantas limitations. In particular, although the processes have beendescribed by examples, the stages of the processes can be performed in adifferent order than illustrated or simultaneously. Furthermore, to theextent that the terms “including”, “includes”, “having”, “has”, “with”,or variants thereof are used in the detailed description, such terms areintended to be inclusive in a manner similar to the term “comprising.”As used herein, the terms “one or more of” and “at least one of” withrespect to a listing of items such as, for example, A and B, means Aalone, B alone, or A and B. Further, unless specified otherwise, theterm “set” should be interpreted as “one or more.” Also, the term“couple” or “couples” is intended to mean either an indirect or directconnection. Thus, if a first device couples to a second device, thatconnection can be through a direct connection, or through an indirectconnection via other devices, components, and connections.

Those skilled in the art will be able to make various modifications tothe described implementations without departing from the true spirit andscope. The terms and descriptions used herein are set forth by way ofillustration only and are not meant as limitations. In particular,although the method has been described by examples, the steps of themethod can be performed in a different order than illustrated orsimultaneously. Those skilled in the art will recognize that these andother variations are possible within the spirit and scope as defined inthe following claims and their equivalents.

The foregoing description of the disclosure, along with itsimplementations, has been presented for purposes of illustration only.It is not exhaustive and does not limit the disclosure to the preciseform disclosed. Those skilled in the art will appreciate from theforegoing description that modifications and variations are possible inlight of the above teachings or may be acquired from practicing thedisclosure. For example, the steps described need not be performed inthe same sequence discussed or with the same degree of separation.Likewise various steps may be omitted, repeated, or combined, asnecessary, to achieve the same or similar objectives. Similarly, thesystems described need not necessarily include all parts described inthe implementations, and may also include other parts not describe inthe embodiments.

Accordingly, the disclosure is not limited to the above-describedimplementations, but instead is defined by the appended claims in lightof their full scope of equivalents.

What is claimed is:
 1. A system for distributing wireless signals intelecommunication networks, the system comprising: a server computercomprising one or more processors and one or more memory devices,wherein the one or more memory devices store instructions that, whenexecuted by the one or more processors, provide functions of a pluralityof baseband units in a mobile network and pool baseband resources of theplurality of baseband units; a point of interface unit coupled to adistributed antenna system implementing the mobile network, wherein thedistributed antenna system distributes signals received from theplurality of baseband units; and an interface link coupled to the servercomputer and the point of interface unit, wherein the server computercomprises at least one electronic connection card coupled to the pointof interface unit of the distributed antenna system through theinterface link, wherein the point of interface unit comprises a commonpublic radio interface (CPRI) slave interface and a CPRI masterinterface, and wherein the point of interface unit is coupled to the atleast one electronic connection card through the CPRI slave interface,and is coupled to one or more additional point of interface unitsthrough the CPRI master interface or through the CPRI slave interface.2. The system of claim 1, wherein the interface link comprises one ormore optical connecting links.
 3. The system of claim 1, wherein theinterface link utilizes one or more communication protocols selectedfrom a common public radio interface (CPRI) protocol and Ethernetprotocol.
 4. The system of claim 1, wherein the least one electronicconnection card is a peripheral component interface (PCI) card.
 5. Thesystem of claim 1, wherein the one or more memory devices storeinstructions that, when executed by the one or more processors, providean operational and maintenance terminal and an interface to theoperational and maintenance terminal.